-
Notifications
You must be signed in to change notification settings - Fork 430
[dbt] Explain new 'on_schema_change' config available for MVs #5192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
koletzilla
wants to merge
2
commits into
main
Choose a base branch
from
dbt-clickhouse/documentation-updates-20260112
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…aterialized views
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
dhtclk
approved these changes
Jan 9, 2026
BentsiLeviav
requested changes
Jan 11, 2026
docs/integrations/data-ingestion/etl-tools/dbt/features-and-configurations.md
Outdated
Show resolved
Hide resolved
…nfigurations.md Co-authored-by: Bentsi Leviav <[email protected]>
| > you will encounter the following warning: | ||
| `Warning - Table <previous table name> was detected with the same pattern as model name <your model name> but was not found in this run. In case it is a renamed mv that was previously part of this model, drop it manually (!!!) ` | ||
|
|
||
| #### How to iterate the target table schema {#how-to-iterate-the-target-table-schema} |
Contributor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The title and text use “iterate the target table schema.” feels a bit unclear to me, do you happen to have other suggestions?
BentsiLeviav
approved these changes
Jan 15, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Checklist